Simultaneously broadcasting acknowledgements of reception of uplink wireless communication

ABSTRACT

Apparatuses, methods, and systems for communicating through a wireless link are disclosed. A method includes scheduling, by a server, communication between a base station and a plurality of hubs, receiving, by the base station, the scheduled communication, providing, to each hub, a data profile that includes a periodicity, an offset, and a carrier frequency based on the scheduled communication, receiving, by the base station, uplink wireless communication from each of the plurality of hubs according to the data profile of each of the hubs and according to the scheduled communication, and simultaneously broadcasting, by the base station, acknowledgements of reception of uplink wireless communication from each of the plurality of hubs.

RELATED APPLICATIONS

This patent application is a continuation-in-part (CIP) of U.S. patentapplication Ser. No. 16/396,651, filed Apr. 27, 2019, titled“Coordinated Access to a Satellite Link using Data Profiles”, which ishereby incorporated by reference.

FIELD OF THE DESCRIBED EMBODIMENTS

The described embodiments relate generally to wireless communications.More particularly, the described embodiments relate to systems, methodsand apparatuses for simultaneously broadcasting, by the base station,acknowledgements of reception of uplink wireless communication.

BACKGROUND

Current data networks are designed primarily for human users and thenetwork and traffic characteristics that human users generate. Thegrowth and proliferation of low-cost embedded wireless sensors anddevices pose a new challenge of high volumes of low bandwidth devicesvying for access to limited network resources. One of the primarychallenges with these new traffic characteristics is the efficiency atwhich the shared network resources can be used. For common low bandwidthapplications such as GPS tracking, the efficiency (useful/useless dataratio) can often be below 10%. This inefficiency is the result of largevolumes of devices communicating in an uncoordinated environment.Addressing this problem is fundamental to the future commercialviability of large-scale sensor network deployments.

It is desirable to have methods, apparatuses, and systems forsimultaneously broadcasting, by the base station, acknowledgements ofreception of uplink wireless communication.

SUMMARY

An embodiment includes a method of communicating through a wirelesslink. The method includes scheduling, by a server, communication betweena base station and a plurality of hubs, receiving, by the base station,the scheduled communication, providing, to each hub, a data profile thatincludes a periodicity, an offset, and a carrier frequency based on thescheduled communication, receiving, by the base station, uplink wirelesscommunication from each of the plurality of hubs according to the dataprofile of each of the hubs and according to the scheduledcommunication, and simultaneously broadcasting, by the base station,acknowledgements of reception of the uplink wireless communication fromeach of the plurality of hubs, wherein at least one of the plurality ofhubs receives and determines whether uplink wireless communication fromthe at least one of the plurality of hubs was successfully receivedbased at least on utilization of at least the periodicity, the offset,and the carrier frequency of the data profile of the at least one of theplurality of hubs.

Another embodiment includes a wireless system. The system includes aserver, the server operative to schedule communication between a basestation and a plurality hubs, through wireless links. The base stationis operative to receive the scheduled communication, provide to each huba data profile that includes a periodicity, an offset, and a carrierfrequency based on the scheduled communication, receive uplink wirelesscommunication from each of the plurality of hubs according to the dataprofile of each of the hubs and according to the scheduledcommunication, and simultaneously broadcast acknowledgements ofreception of the uplink wireless communication from each of theplurality of hubs, wherein at least one of the plurality of hubsreceives and determines whether uplink wireless communication from theat least one of the plurality of hubs was successfully received based atleast on utilization of at least the periodicity, the offset, and thecarrier frequency of the data profile of the at least one of theplurality of hubs.

Other aspects and advantages of the described embodiments will becomeapparent from the following detailed description, taken in conjunctionwith the accompanying drawings, illustrating by way of example theprinciples of the described embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a plurality of hubs that communicate data of data sourcesthrough a satellite link to a base station, according to an embodiment.

FIG. 2 shows uplink and downlink frames of wireless communication,according to an embodiment.

FIG. 3 is a flow chart that includes steps of a method of simultaneouslybroadcasting, by the base station, acknowledgements of reception of theuplink wireless communication, according to an embodiment.

FIG. 4 shows a plurality of hubs that communicate data of data sourcesthrough a satellite link to a base station, according to an embodiment.

FIG. 5 shows packet interference due to variations in propagation timebetween the base station and multiple different hubs, according to anembodiment.

FIG. 6 shows multiple sources for providing updates or feedback of dataprofiles, according to an embodiment.

FIG. 7 shows data profiles, according to an embodiment.

FIG. 8 shows results of data smoothing due to data source profileadjustment, according to an embodiment.

FIG. 9 shows control channel efficiencies and the effects assignments ofpreamble codes can have on the control channel efficiencies, accordingto an embodiment.

FIG. 10 a dynamic allocation of control channel versus data channel,according to an embodiment.

FIG. 11 is a flow chart that includes steps of a method of coordinatingaccess of a plurality of devices across a satellite link, according toan embodiment.

FIG. 12 shows a plurality of hubs that communicate data of data sourcesthrough a shared resource to a base station, according to an embodiment.

FIG. 13 shows a series of NBIOT communications between a server, a basestation, a modem of a hub, and a hub, according to an embodiment.

DETAILED DESCRIPTION

The embodiments described include methods, apparatuses, and systems forsimultaneously broadcasting acknowledgements of reception of the uplinkwireless communication. For at least some embodiments, a serverschedules communication between a base station and a plurality of hubs.For an embodiment, the base station receives the scheduled communicationwhich the base station can provide to each of the plurality of hubs.Each hub is provided with a data profile that includes a periodicity, anoffset, and a carrier frequency based on the scheduled communication.The base station receives uplink wireless communication from each of theplurality of hubs according to the data profile of each of the hubs andaccording to the scheduled communication. Finally, the base stationsimultaneously broadcasts acknowledgements of reception of the uplinkwireless communication from each of the plurality of hubs. For anembodiment, each hub uses the periodicity, the offset, and the carrierfrequency within the data profile to facilitate at least one of theuplink communication and/or the reception of acknowledgement of theuplink communication through reception of the simultaneously broadcastacknowledgements.

FIG. 1 shows a base station 140 wirelessly communicating with aplurality of hubs 110, 190, according to an embodiment. For anembodiment, a server 150 operates to generate scheduling of the wirelesscommunication between the base station 140 and the plurality of hubs)110, 190 through wireless links 115, 116. For an embodiment, the server150 may access a database 160, aid in generating the scheduledcommunication, and provide the scheduled communication to the basestation 140. For an embodiment, the scheduled communication includesallocating frequency and time slots for both uplink and downlinkwireless communication. For an embodiment, the base station 140 includesa modem 145 and the hubs 110, 190 include modems 130, 132, for enablingthe wireless communication between the base station 140 and the hubs110, 190.

For an embodiment, the server 150 additionally generates a data profile122, 124 for each of the hubs. For example, the server 150 generates thedata profile that the base station 140 provides to the hub 190. For anembodiment, the data profile includes a periodicity, an offset, and acarrier frequency based on the scheduled communication. For anembodiment, the hub 190 utilizes the periodicity, the offset, and thecarrier frequency of its data profile 124 for determining when and atwhat carrier frequency to transmit uplink wireless communication 187 tothe base station 140.

For an embodiment, the base station 140 then receives uplink wirelesscommunication from each of the plurality of hubs 110, 190 according tothe data profile of each of the hubs 110, 190 and according to thescheduled communication. For an embodiment, the hubs 110, 190 use thedata profiles 122, 124 for determining when to transmit, and the basestation 140 uses the scheduled communication to determine when toreceive the uplink wireless communication.

For an embodiment, after the time period of the scheduled communication,the base station 140 simultaneously broadcasts acknowledgements 188 ofreception of the uplink wireless communication from each of theplurality of hubs 110, 190. That is, the simultaneously broadcastacknowledgement 188 includes acknowledgments directed to each of theindividual hubs 110, 190 and indicates whether the scheduled uplinkcommunication received from each of the individual hubs 110, 190 wassuccessfully received. Each of the individual hubs 110, 190 candetermine whether its uplink wireless communication was successfullyreceived based on reception of the broadcast acknowledgement 188. Thatis, each of the hubs 110, 190 determine whether the uplink wirelesscommunication was successful based on the simultaneously broadcastacknowledgements, wherein reception of the simultaneously broadcastacknowledgements by each hub is facilitated by the data profile of thehub. For an embodiment, the hub utilizes the periodicity, the offset,and the carrier frequency within the data profile to determine oridentify acknowledgements of uplink communication of the hub to the basestation.

For an embodiment, the broadcast acknowledgement 188 originates at theserver 150. For an embodiment, the broadcast acknowledgement 188originates at the base station 140.

By including the acknowledgments of many hubs within a single broadcastacknowledgement rather than generating a separate transmittedacknowledgment for each individual hub saves wireless communicationair-time. This becomes more and more true as the number of hubsincreases.

As shown, for an embodiment, the uplink wireless communication istransmitted by plurality of hubs and received by the base stationthrough a satellite wireless link via a satellite 191, and the basestation simultaneously broadcasts the acknowledgements through thesatellite wireless link.

FIG. 2 shows uplink and downlink frames 210, 220 of wirelesscommunication, according to an embodiment. The scheduled communicationincludes uplink communication allocations for each of the hubs 110, 190.As shown, the uplink frame includes uplink wireless communicationallocations for a hub1 and a hubB2 at different time and frequency slotswithin the uplink frame 210.

For an embodiment, the data profile for each hub includes at least onetime and frequency slot for uplink communication of the hub. For anembodiment, the data profile for the hub further includes at least onetime and frequency slot for reception of broadcast acknowledgments thehub. That is, not only does the data profile provide the hub with thescheduled uplink wireless communication, the data profile additionallyincludes scheduling of the downlink broadcast acknowledgements. For anembodiment, the acknowledgements can be extracted by hub from thesimultaneous broadcast acknowledgement 220 by using the schedule(provided as part of user-profile) used by hub for uplink communication.

Further, for an embodiment, the hub determines which of one or more bitsof a received broadcast acknowledgement packet within the simultaneousbroadcast acknowledgement of the downlink frame 220 includesacknowledgment information of the hub based on the scheduled time andfrequency slots for uplink communication of the hub. For example, asshown, a packet 230 within the simultaneous broadcast acknowledgement ofthe downlink frame 220 includes the acknowledgement information of eachof the plurality of hubs. Each hub can determine which bit(s) of thepacket 230 within simultaneous broadcast acknowledgement of the downlinkframe 220 includes the acknowledgement information direction to the hubbased on the information within the data profile of the hub, or based onthe time and frequency slot the hub used in its uplink wirelesscommunication. For an embodiment, the location of acknowledgement foruplink communication during a specific time slots-subcarrier withinsimultaneous broadcast acknowledgement can be determined by user deviceusing the schedule (for example, timeslot and sub-carrier frequency)used for uplink transmission.

As previously described, for an embodiment, the scheduled communicationthat is provided to the base station includes time slots and carrierfrequencies, and includes an allocation of at least some of the timeslots and subcarrier frequencies. That is, at least some of the time andfrequency slots are allocated by the scheduled communication provided tothe base station by the server. For an embodiment, the scheduledcommunication includes sub-frames. For a specific embodiment, asub-frame includes 1 millisecond timeslots as specified NB-IOT(Narrow-Band Internet of Things) standards. For an embodiment, thescheduled communication includes user information (such as, userIdentity), data transmission mode and connection related information forthe user for which timeslots and sub-carrier frequencies (resourceunits) are allocated.

For at least some embodiment, the base station receives the scheduledcommunication in the form of allocated time and frequency slots, and thebase station further allocates additional time slots and carrierfrequencies. For an embodiment, the further allocating includes thereceiving, by the base station, subsequent requests and demands that thebase station adapts and infills the additional time slots and carrierfrequencies. For an embodiment, the base station receives a time periodthat is allocated to the base station, and the base station then selectstime slots and sub-carriers within the time period for the scheduledcommunication.

For at least some embodiments, the base station receives the uplinkcommunication from the hubs, and collects acknowledgements for scheduleduplink communication in a hyper frame/radio frame/subframe (or a fixedtime duration) and sub-carrier frequency range, and creates a broadcastpacket (the simultaneously broadcast acknowledgements). For anembodiment, the base station then broadcasts the broadcast/multicastpacket (the simultaneously broadcast acknowledgements) at a set timedelay from completion of a time window used for collection ofacknowledgements of the scheduled uplink communication. This broadcastincludes acknowledgement of receiving packets (the uplink communication)successfully in a frequency and time slot within the given time window.

For an embodiment, the data profile of the user device facilitatesreception of the simultaneously broadcast acknowledgements through atleast an acknowledgement period and an acknowledgement offset includedwithin the data profile of the hub that allows the hub to determine whento receive simultaneously broadcast acknowledgements of uplink wirelesscommunication of the hub.

For an embodiment, each simultaneously broadcast acknowledgementincludes acknowledgement information of a plurality of hubs thattransmitted uplink wireless communication within a corresponding periodof time t2-t1, and frequency (subcarrier) allocation. For an embodiment,this includes timeslots within subcarrier allocations within the t2-t1time duration, wherein the subcarrier allocation may or may not becontinuous within a range of subcarriers, and the time slots may or maynot by continuous in time, forming a checkerboard of time slots andsubcarrier frequencies within the t2-t1 time duration.

For an embodiment, the simultaneously broadcast acknowledgements includesimultaneously multicast acknowledgements, wherein an acknowledgment foreach of the user devices within the simultaneously multicastacknowledgements include a code that a corresponding set of hubs candecode. For an embodiment, hubs with acknowledgements in simultaneousmulticast acknowledgement share a code to decode the simultaneousmulticast acknowledgement. For an embodiment, the code for multicastacknowledgements is provided with the data profiles. For an embodiment,the code includes a scrambling code.

For an embodiment, the acknowledgment for each of the hubs within thesimultaneously broadcast acknowledgements provides an acknowledgment tothe hub for uplink wireless communication within a specified number oftime slots and carrier frequencies.

For an embodiment, the data profile includes the periodicity, offset,and carrier frequency for the uplink wireless communication, and anacknowledgement periodicity, and an acknowledgement offset ofacknowledgements of the uplink wireless communication within thesimultaneously broadcast acknowledgements. For an embodiment, the dataprofiles also include a transmission mode, which can include RRC (RadioResource Control) message type and data transmission mode for uplinkwireless communication.

FIG. 3 is a flow chart that includes steps of a method of simultaneouslybroadcasting, by the base station, acknowledgements of reception of theuplink wireless communication, according to an embodiment. A first step310 includes scheduling, by a server, communication between a basestation and a plurality of hubs). A second step 320 includes receiving,by the base station, the scheduled communication. A third step 330includes providing, to each hub, a data profile that includes aperiodicity, an offset, and a carrier frequency based on the scheduledcommunication. A fourth step 340 includes receiving, by the basestation, uplink wireless communication from each of the plurality ofhubs according to the data profile of each of the hubs and according tothe scheduled communication. A fifth step 650 includes simultaneouslybroadcasting, by the base station, acknowledgements of reception of theuplink wireless communication from each of the plurality of hubs.

As previously described, for an embodiment, the uplink wirelesscommunication is transmitted by the plurality of hubs and received bythe base station through a satellite wireless link, and the base stationsimultaneously broadcasts the acknowledgements through the satellitewireless link.

As previously described, at least some embodiments include determining,by each of the hubs, whether the uplink wireless communication wassuccessful based on the simultaneously broadcast acknowledgements,wherein reception of the simultaneously broadcast acknowledgements byeach hub is facilitated by the data profile of the hub. For anembodiment, the data profile includes at least one time and frequencyslot for uplink communication of the hub. For an embodiment, the dataprofile further includes at least one time and frequency slot forreception of broadcast acknowledgments the hub. At least someembodiments further include determining, by the hub, which of one ormore bits of a received broadcast acknowledgement packet includesacknowledgment information of the hub based on the scheduled time andfrequency slots for uplink communication of the hub.

As previously described, for at least some embodiments the scheduledcommunication provided to the base station includes time slots andcarrier frequencies, and includes an allocation of at least some of thetime slots and subcarrier frequencies. At least some embodiments includeallocating, by the base station, additional time slots and carrierfrequencies. For at least some embodiments the allocating includes thereceiving, by the base station, subsequent requests and demands that thebase station adapts and infills the additional time slots and carrierfrequencies.

As previously described, for at least some embodiments the data profileof the user device facilitates reception of the simultaneously broadcastacknowledgements through at least an acknowledgement period and anacknowledgement offset included within the data profile of the hub thatallows the hub to determine when to receive simultaneously broadcastacknowledgements of uplink wireless communication of the hub.

As previously described, for at least some embodiments eachsimultaneously broadcast acknowledgement includes acknowledgementinformation of a plurality of hubs that transmitted uplink wirelesscommunication within a corresponding period of time t2−t1, andsubcarrier frequencies.

As previously described, for at least some embodiments thesimultaneously broadcast acknowledgements include simultaneouslymulticast acknowledgements, wherein an acknowledgment for each of theuser devices within the simultaneously multicast acknowledgementsinclude a code that a corresponding set of hubs can decode.

As previously described, for at least some embodiments an acknowledgmentfor each of the hubs within the simultaneously broadcastacknowledgements provides an acknowledgment to the hub for uplinkwireless communication within a specified number of time slots andcarrier frequencies.

As previously described, for at least some embodiments the hub profileincludes the periodicity, offset, and carrier frequency for the uplinkwireless communication, and an acknowledgement periodicity, and anacknowledgement offset of acknowledgements of the uplink wirelesscommunication within the simultaneously broadcast acknowledgements.

For at least some embodiments, the data profile allows a range ofnetwork access techniques to be simultaneously supported on a hub. Thisallows, for example, a hub that includes a data device such as atemperature sensor and another data device such as a mobile point ofsale terminal to employ multiple data reporting techniques. For at leastsome embodiments, the data profiles allow routing and management of thedata on a per packet level rather than on a data device level. That is,for example, the data profile of a data device may dictate thatdifferent packets of the data device may be communicated or reporteddifferently. For example, temperature data (packets) may be reportedperiodically, but if the temperature exceeds a specified level, thetemperature data (packets) is reported in real-time.

For an embodiment, channel and transmission characteristics are known apriori for deterministic data types which can be used to significantlyreduce the overhead on the network spent on passing this informationbetween a hub and a base station. For at least some embodiments,transmissions by a hub of multiple disparate devices can be coordinatedby a network management element via the data profiles andsynchronization (that is, synchronization between different datadevices) of packets provides traffic spreading and reduces the need forrandom access and other channel contention resources. For at least someembodiments, hub transmission timing can be coordinated betweengeographically disparate devices to eliminate the contention for sharednetwork resources only for applicable application types such as periodicor schedule data while preserving the flexibility of real timetransmissions.

FIG. 4 shows a plurality of hubs 410, 490 that communicate data of datasources 411, 412, 413, 414, 415 through satellite link(s) 415, 416 to abase station 140, according to an embodiment. As shown, the data sources411, 412, 413, 414, 415 are connected to the hubs 410, 490. The hubs410, 490 communicate through modems 430, 432 to a modem 145 of the basestation 440 through the wireless satellite links 415, 416. The basestation may also communicate with outside networks 470, 480. For anembodiment, the wireless satellite links 415, 416 reflectively passthrough a satellite 491.

It is to be understood that the data sources 411, 412, 413, 414, 415 canvary in type, and can each require very different data reportingcharacteristics. The wireless satellite links 415, 416 links are alimited resource, and the use of this limited resource should bejudicious and efficient. In order to efficiently utilize the wirelesssatellite links 415, 416, each of the data sources 411, 412, 413, 414,415 are provided with data profiles (shown as Dev profiles as a profilemay be allocated for each device) 421, 422, 423, 424, 425 thatcoordinate the timing (and/or frequency) of reporting (communication bythe hubs 410, 490 to the base station 440 through the wireless satellitelinks 415, 416) of the data provided by the data sources 411, 412, 413,414, 415.

For an embodiment, a network management element 450 maintains a database160 in which the data profiles 421, 422, 423, 424, 425 can be stored andmaintained. For an embodiment, the network management element 450 is anembodiment of the previously described server 150. For an embodiment,the network management element 450 manages the data profiles 421, 422,423, 424, 425, wherein the management includes ensuring thatsynchronization is maintained during the data reporting by the hubs 410,490 of the data of each of the data sources 411, 412, 413, 414, 415.That is, the data reported by each hub 410, 490 of the data of the datasources 411, 412, 413, 414, 415 maintains synchronization of the datareporting of each of the data sources 411, 412, 413, 414, 415 relativeto each other. Again, the network management element 450 ensures thissynchronization through management of the data profiles 421, 422, 423,424, 425. The synchronization between the data sources 411, 412, 413,414, 415 distributes the timing of the reporting of the data of each ofthe data sources 411, 412, 413, 414, 415 to prevent the reporting of onedevice from interfering with the reporting of another device, andprovides for efficiency in the data reporting.

For at least some embodiments, the network management element 450resides in a central network location perhaps collocated with multiplebase stations and/or co-located with a network operations center (asshown, for example, in FIG. 6). For an embodiment, the networkmanagement element 450 directly communicates with the base station 440and initiates the transfer of data profiles across the network via thebase station 440 to the hubs 410, 490.

For at least some embodiments, data profiles are distributed when newhubs are brought onto the network, when hubs change ownership, or whenthe hubs are re-provisioned. Other changes to data profile contentsoutside of these situations are more likely addressed by sync packets(for an embodiment, a sync packet is a packet to update the value of aspecific field inside of a data profile, but not necessarily updatingthe structure of the data profile) where only small changes to profilefields are required.

As described, the data profiles 421, 422, 423, 424, 425 control timingof when the hubs 410, 490 communicate the data of the data sources 411,412, 413, 414, 415 through wireless satellite links 415, 416 (sharedresource). Accordingly, the described embodiments coordinate access tothe shared network resource (wireless satellite links 415, 416) toinsure optimal usage of the network resource to avoid collisions betweenpackets, the transmission of redundant information, and to reshapeundesired traffic profiles.

For at least some embodiments, the data profiles allow for theelimination of redundant data channel setup information which is alreadycontained inside the data profile, which then are no longer needed to beshared upon the initiation of every packet sent across the network. Thisinformation may include the transmission size, sub-carrier (frequency)allocation, MCS (modulation and coding scheme) selection, and timinginformation. The result of this is a reduction in data resourcesconsumed by the network to send a packet of data. In the example ofsending a GPS data packet containing x, y, z, and time, the amount ofredundant channel setup information is 8× larger than the actual GPSdata packet of interest, resulting in a very inefficient network forlarge volumes of narrowband traffic. Additionally, in the realm ofsatellite communications, the elimination of unnecessary channel setupmessages reduces the latency between the initiation of sending, forexample, a GPS packet across the network and actually receiving thatpacket by roughly half. For example, a normally 3 second latency can bereduced to as low as 0.25 seconds.

While FIG. 4 shows each hub as including more than one data source, itis to be understood that each hub may include a single data source.Further, the data of a single data source may be treated differentlybased on the profile. That is, different data packets of the single datasource may be reported, or communicated differently based on the profileof the data device. For example, some data of the data source may bereported or communicated periodically, whereas different data of thedata source may be reported or communicated in real time. For anembodiment, characteristics or properties of the data determine orinfluence the timing of the communication of the data from the hub ofthe data source.

Further, while FIG. 4 shows the hubs and the data sources possibly beingseparate physical devices, it is to be understood that the hub and oneor more data devices may actually be a single physical device.

FIG. 5 shows packet interference due to variations in propagation timebetween the base station 540 and multiple different hubs 510, 512,according to an embodiment. As shown, a first hub (Hub 1) 510 has atransit time of wireless communication (link 515) between the first hub(Hub 1) 510 and a satellite 590 of T1. Further, as a second hub (Hub 2)512 has a transit time of wireless communication (link 516) between thesecond hub (Hub 2) 512 and the satellite 590 of T2. The variations ofthe transmit times between different hubs can be large due to thepotentially large wireless coverage footprint of the satellite 591.

For at least some embodiments, transmission delay of wirelesscommunication between hubs 510, 512 and the base station 540 includesthe summation of at least two components, a course delay and a finedelay. The course delay consists of the minimum delay seen by all hubscommunicating to a single base station. Each base station therefore hasa single course delay associated with the base station. For anembodiment, the fine delay is the addition of a delay variance across alarge geography served by a base station. Therefore, the fine delay isdefined on a per hub basis.

For an embodiment, the course delay is transmitted to the hubs 510, 512and stored in the data profile from the network management element viathe base station 540. For an embodiment, the fine delay is similarlytransmitted across the network, or it may be independently inferredbased upon hub location.

An interference condition can result due to the potentially varyingpropagation times between the hubs 510, 512 and the base station 540through the wireless satellite links. For example, as additionally shownin FIG. 2, a packet 530 transmitted from the first hub (Hub 1) 510 tothe base station 540 has the first transmit time T1 to the satellite591. Further, as additionally shown in FIG. 5, a packet 532 transmittedfrom the second hub (Hub 2) 512 to the base station 540 has the secondtransmit time T2 to the satellite 591. Accordingly, a packet interferingcondition 542 can result when a packet 534 received at the base station540 from the first hub (Hub 1) 510 is received at the same time that apacket 536 received at the base station 540 from the second hub (Hub 2)512 is received.

To mitigate the packet interference condition shown in FIG. 5, for atleast some embodiments, the profile for each device is adjusted based atleast in part on a location of the device, wherein the profileadjustment mitigates differences in propagation time of communicationpropagating from each hub to the base station. That is, for example, aGPS (global positioning sensor) device of the hub provides the locationof the hub. The hub can then adjust the profiles of the data devicesassociated with the hub based on the location of the hub to reduce thepossibility of packet interference due to data reporting by other hubsof data from other date devices.

While this functionality is described using location data, otherembodiments to determine the fine propagation delay include timing ofpreamble positions inside a random access window, signal strengthdetection, or general timing of sync signals

The data profiles of the data source may initially be selected tosynchronize the data reporting. However, due to the differences inpropagation through wireless links to the base station, the describedinterference condition can occur. As described, for an embodiment, thehub reporting the data of the data devices can adjust the profiles toaccount for the differences in propagation delay. For an embodiment, thedifferences in the propagation delay can be accounted for by the GPSlocations of multiple hubs. The data profiles can then be adjusted toaccount for the differences in wireless transmission propagation delaybetween reporting hubs. For an embodiment, the propagation time isdetermined by a time-of-flight of communication between the hub 510 andthe base station 540. The differences in the propagation delays can thenbe accounted for in the data profiles to mitigate interferences betweenreporting hubs.

FIG. 6 shows multiple sources for providing updates or feedback of dataprofiles, according to an embodiment. As described, for an embodiment,the network management element manages the data profiles 421, 422, 423,424, 425 of the data devices 411, 412, 413, 414, 415. At least someembodiments include adjusting the data profile. At least one embodimentincludes the data profile adjustment 664 by sourced by a downstreamdevice, such as, one or more of the hubs 410, 490. At least one otherembodiment includes the data profile adjustment 662 being sourced by,for example, a network operation center 650.

As stated, for at least some embodiments, the data profiles areadaptively updated based on a top down feedback from the networkoperation center 650 or the network management element 450. For anembodiment, this includes rebalancing preamble codes assigned todifferent data devices to smooth RACH (random access channel) profiles,which is triggered, for example, by the detection of excess (greaterthan a threshold amount) collisions between RACH packets. For anembodiment, the rebalancing includes assigning to the offending devicesdisparate orthogonal preamble codes to mitigate the collisions. For anembodiment, this includes adjusting timing offsets (adjusting the timingoffset includes adjusting the relative timing of periodic reporting) tosmooth network traffic congestion and maintain network utilization forperiodic data below X %, by measuring allocated versus free networkresource units. For an embodiment, this includes updating data profileswhen changing an application of a data device, triggered by user/owneroperator intervention, for example, via a web console. For anembodiment, this includes updating the course round trip delay timing,triggered, for example, by a new hub registration on a base station.

As stated, for at least some embodiments, the data profiles areadaptively updated based on a bottom up feedback from the hubs 410, 490or the data sources 411, 412, 413, 414, 415. For an embodiment, thisincludes the previously described fine round-trip timing delay,constantly updated within the data profiles based upon GPS coordinatesof the hubs 410, 490. For an embodiment, this includes the data profileof a data device being updated by a hub through a communication link tothe hub. For example, a user/operator may proactively update a profilethrough the hub by connecting via wireless phone to the hub. This can beuseful, for example, when the hub is located in a remote location thatis not serviced by a cellular network, and therefore, a user/operatorhas no way of connecting to the network operation center 650 or thenetwork management element 450 without the wireless satellite connectionprovided by the hub. The only way for the user/operator to update one ormore of the data profiles is through the bottom up feedback provided bythe hub.

FIG. 7 shows data profiles, according to an embodiment. The dataprofiles provide coordination of the communication of the data of thedata devices over the shared wireless satellite links. The communicationcan include one or more of real time data reporting, scheduled datareporting, and/or periodic data reporting. The data profile for a givendata device provides the hub associated with the data device the abilityto control a timing of communication of the data for each of the one ormore data sources from the hub to a base station through the wirelesssatellite link. The controlled timing provides for synchronization ofthe communication of the data with respect to the communication of dataof other data sources of both the same hub, and for one or moredifferent hubs. For an embodiment, the data profile additionallyprovides the hub with a frequency allocation for the communication ofthe data of the data source.

An exemplary generic data profile 710 of FIG. 7 includes enablement ofreal time access or real time reporting of the data of the data device,enablement of scheduled access or scheduled reporting of the data of thedata device, and enablement of periodic access or periodic reporting ofthe data of the data device. Further, for an embodiment, the dataprofile also includes an estimated MCS (modulation and coding scheme).Further, for an embodiment, the data profile also includes a dataprocessing function.

A specific example of a data profile 720 provides for reporting of thelocation of a data device. This could be, for example, the reporting ofdata of a data device associated with a vehicle. For this embodiment,both the real time data reporting and the periodic data reporting areenabled, but the scheduled reporting is not enabled. Specifically, theperiodic reporting is specified to report once every 15 minutes,beginning at 12:00 (noon). Further, the reporting packet includes amessage size of 16 bytes, wherein the preamble codes and the MCS arespecified. The data profile 720 includes a specific data processingfunction. The exemplary function includes determining whether the datadevice (and therefore, the vehicle associated with the data device) iswithin a geographical fence. While the data device is within thegeographical fence, the data device follows the periodic reportingschedule as specified by the data profile. If the data device isdetected to leave an area specified by the geographical fence, the realtime reporting flag is triggered, and the hub of the data deviceperforms real time communication with the base station that includes,for example, the location of the data device as detected outside of thegeographical fence.

FIG. 8 shows results of data smoothing due to data source profileadjustment, according to an embodiment. As shown in FIG. 8, the dataprofile can be used to smooth the communication of data of a data sourcefrom a hub of the data source to a base station. As shown, beforeselecting and/or adjusting the data profile, the channel resourcerequest of a particular data device may exceed the resources available(service limit) through the wireless satellite link. However, afterselecting and/or adjusting the data profile, the timing of thecommunication can be selected to smooth the data reporting which doesnot exceed the service limit of the wireless satellite link.

For at least some embodiments, data traffic of reporting data devices issmoothed to yield channel resource requests to below a service limitthreshold (shown as the service limit in FIG. 5) by adjusting a phaseoffset with the data profile of periodic reporting of data of one ormore data devices. As previously stated, the adjusting the phase offsetincludes adjusting a relative timing of the reporting of periodic data.For an embodiment, the phase offsets of the data profiles of differentdata devices are spread over wider widows of time. Inferiorimplementations may select convenient times, such as, on the hour, or onthe half hour. However, the described embodiments include adjustments ofthe phase offset of different devices which provides for the smoothingof the data traffic.

For at least some embodiments, data traffic of reporting data devices issmoothed by adjusting for certain applications the periodicity of thedata reporting of different data devices. For an embodiment, thisincludes adjusting the periodicity to reflect current networkconditions. As an example, applications of data devices under certainSLAs (service level agreements) may have their periodicity reducedduring peak usage hours which may be found, for example, during harvestseason, holidays, or other time periods where human/machine interactionsincrease. Peak usage hours can be identified a priori or can beidentified by monitoring traffic conditions over time, and identifyinghigh (greater than a threshold) periods of data traffic.

FIG. 9 shows control channel efficiencies and the effects assignments ofpreamble codes can have on the control channel efficiencies, accordingto an embodiment. Before intelligent assignment of preamble codes, theefficiency of a control channel may have the characteristics of curve910. That is, the efficiency of the control channel may increase as thenumber of devices increases. However, at some point, as the number ofdevices increases, the efficiency levels off, and then greatly decreaseswith increases in the number of devices.

However, by intelligently selecting preambles for packets of reportingdata, the efficiency of the control channel can be improved greatly asshown by curve 920. For example, reporting times of different datadevices of different hubs can be monitored over time. Based on themonitoring, preamble codes for different devices can be selected suchthat devices that typically report at common times have orthogonalcodes. The assignment of orthogonal codes reduces the possibility of thepackets of these devices from interfering with each other. Further, thetiming of the reporting can be adjusted through the data profiles.

For at least some embodiments, the network management element curatesmeta-data about the data devices and data sources connected to thenetwork through the base stations. For an embodiment, this meta-dataincludes RACH probability density functions. For an embodiment, theseprobability density functions are used to optimally assign preamblecodes between devices to minimize the infinity norm of the expectedvalue (highest value) of RACH requests of the same preamble code. TheRACH probability density functions can be determined by monitoring theactivity during specified RACH periods of operation.

FIG. 10 shows a dynamic allocation of control channel versus datachannel, according to an embodiment. A first control channel allocation1010 occupying a first amount of frequency and time resources of thewireless link.

The resources allocated to the control channel can be reduced withutilization of intelligent preamble assignments within the data sourceprofiles. A second control channel allocation 1020 occupying a secondamount of frequency and time resources of the wireless link which isless than the first control channel allocation 1010.

Without “intelligent” preamble code allocations, maximum efficiency ofcontrol channel is 1/e, resulting in excess radio resources(time/frequency) being allocated to RACH (random access channel) whichcould have otherwise been allocated to data. The size of the RACHcontrol window can also have its requirements reduced through the use ofthe fine control adjustments to the roundtrip timing when using thelocation-based embodiment shown in FIG. 2.

FIG. 11 is a flow chart that includes steps of a method of coordinatingaccess of a plurality of devices across a satellite link, according toan embodiment. A first step 1110 includes providing, by each of aplurality of hubs, a unique identifier to a network management elementassociated with a base station, wherein the providing includeswirelessly transmitting, by each of the hubs, the unique identifier tothe base station through a wireless satellite link. A second step 1120includes receiving through the wireless satellite link, by each hub, oneor more data profiles back from the network management element whereineach of the one or more data profiles correspond with one or more datasources associated with the hub. A third step 1130 includes receiving,by each hub, data from the one or more data sources associated with thehub. A fourth step 1140 includes controlling, by each hub, a timing ofcommunication of the data for each of the one or more data sources fromthe hub to the base station through the wireless satellite link based onthe data profile corresponding with the data source, wherein the dataprofile of each of the data sources of each of the hubs maintainsynchronous timing of the communication of the data of each of the datasources of each of the hubs with respect to each other. For at leastsome embodiments, the network management element further allocates perthe data profiles a frequency for the communication between each of thehubs and the base station, for each of the data sources of each of thehubs.

As described, for at least some embodiments, the data profiles controlthe timing of the reporting of the data of the different data sources tosynchronize the data reporting and control (dictate) the radio resource(such as, time and frequency) between the hubs and the base station. Forat least some embodiments, the data profile for each data sourceincludes a rule set for the data source, wherein the rule set controlsthe timing of communication. The rule set of the data profile incontrast to, for example, to a MAC (medium access control) schedule isset and used by the hubs for controlling the communication until thedata profile is updated due to a triggering event.

For an embodiment, the network management element communicates a profileadaptor to one or more of the hubs. For an embodiment, this includes thenetwork management element broadcasting rule sets used by the hub tocontrol/process the data profile(s). For an embodiment, when a hubreceives the profile adaptor, if QOS of the data profile is less than xthen the hub changes, for example, the periodicity of periodictransmissions of a data source for a threshold period of time or untilanother message (such as, another profile adaptor) with a new rule setis received.

For an embodiment, the rule set includes device dependencies of the dataprofile. For example, the rule set may include time and location statesof the data device dependency of the data profile.

For an embodiment, the hub collects the data of the data devices, butdoes not transmit the data until the network management element solicitsthe hub for data transmission. For an embodiment, the hub informs thenetwork management element of restrictions and/or requirements of thehub or the data device associated with the hub. For example, the hub maybe specified by the data profile to transmit once a day, but the hub isavailable to transmit only at a particular time of the day (for example,6 pm to 6 am). The hub may inform the network management element aboutits restrictions/requirements.

For at least some embodiments, the data profile is used to parse (filteror selectively remove or eliminate) raw data from connected datasources. Most commercially available sensors are designed forterrestrial networks and are often overly verbose (include a largeamount of excess data) when transmitting data. A core function of theutilization of the data profile is to understand and map the data schemaof a sensor to extract “filter” only the relevant and most importantinformation. For example, a data report that includes “Engine RPM: 3000”may be filtered by the data profile of the data device down to “3000”which is then interpreted in the context of the data profile. That is,for an embodiment, based upon prior information “standard reporting ofthe specific device” of the specific data devices the data profile isselected to only transmit the selected datums which are a subset of thestandard reporting. This filtering of the reported data intelligentlyreduces the amount of data reported which reduces the demand on theresource (for example, the wireless link) used by each data device.

As previously stated, the described embodiments of the data profilesallow for the elimination of redundant data channel setup informationwhich is already contained inside the data profile, and is no longerneeded to be shared upon the initiation of every packet sent across thenetwork. This information may include the transmission size, sub-carrier(frequency) allocation, MCS selection, and timing information. Theresult of this is a reduction in data resources consumed by the networkto send a packet of data.

Further, as shown for example by the data profile 720 of FIG. 7, thedata profile includes the ruleset for radio resource allocation. As anexample, the ruleset for selecting transmission timing may includeintegrating forward in time a periodic phase offset the integratedperiodicity of periodic reporting. For an embodiment, the ruleset mayinclude user defined functions and routing (for example, geo-fencing ortemperature reporting).

As described, at least some embodiments include the data profile of eachdata device being used to dictate or change radio resource allocationsand general modem operating procedures supported on an applicationlevel. For an embodiment, the data profile of a data device is used tochange, update, or modify link-layer or application layer encryptionschemes as a function of a location of the data device, and/or the timeof day. It may be desirable for a data device to maintain a higher levelof security of reported data based on the location of the data device,and/or the time of reporting of the data of the data device.

For an embodiment, the data profile of a data device is used to change,update, or modify muting or attenuation of a transmission signal powerof the reported data as a function location of the data device, the timeof day, and/or network loading. For at least some embodiments, rulesetsof the data profile are used for directing how and when to do channelestimation of the communication channel of the wireless link between thehub of the data device and the base station. For an embodiment, the dataprofile of the data device controls the timing of the channel estimationbased on the application of the data device. For example, a mobile fleetmanagement application may be directed by the data (device) profile todo channel estimation more often (and/or as a function of velocity) anddifferently than a stationary agriculture sensor. That is, the channelof a mobile device will change more frequently than a stationary device,and the data profile of the mobile device will direct the communicationchannel of the mobile data device to be re-measured more frequently. Foran embodiment, the rulesets of the data profiles control powermanagement of the hub via satellite transmissions of the hub. As anexample, a user case such as fishing where users charge their deviceevery night may utilize higher MCS, less repetitions, more output powerto achieve the most efficient and reliable link possible. Otherapplications such as long-distance trucking may utilize less spectrallyefficient methods to transmit their data, but methods which are moreenergy efficient.

As shown in FIG. 5, at least some embodiments include adjusting the dataprofile for each device based at least in part on a location of thedevice, wherein the data profile adjustment mitigates differences inpropagation time of communication propagating from each hub to the basestation. Further, as described, other methods include determining thedifferences in propagation times based on measured propagation delays.For at least some embodiments, the data profiles for the data deviceinclude a function to calculate a timing advance based upon the location(for example, GPS location) of the data device, and a static location ofthe satellite the hub of the data device is wirelessly linked to thebase station through. For an embodiment, this function of the dataprofile is updated whenever the device transits to a differentsatellite.

For at least some embodiment, a data profile supports multiple datadevices. That is, for example, the network management element determinesa data profile for multiple data devices. For an embodiment, the dataprofile supports multiple data devices with overlapping transmissioncharacteristics. Through management of the data profile, utilization ofthe wireless link between the hub and the base station can be moreefficiently used. That is, transmission overhead, such as, random accesstransmission, and control message overhead, can be more efficient due tothe management of the data profile for multiple data devices. If forexample, two different data devices have data to be transmitted within athreshold duration of time, a single data profile can be managed for thedata devices. The data of the data devices can be merged. For anembodiment, the merging of the data means the data of the different datadevices are transmitted from the hub to the base station using a singledata blob (for example, a data packet) using a single grant message fromthe network management element. For an embodiment, the hub adds aproprietary wrapper/header to define data boundaries and associate datato different devices. For example, wrapper can include a data startindex and a size for each data device.

For at least some embodiments, controlling the timing of thecommunication of the data for each of the one or more data sources fromthe hub to the base station through the wireless link includes selectingthe timing as one of real-time communication, scheduled communication,or periodic communication based on the data profile selected for thedata source. For at least some embodiments, different data sources ofthe hub have different data profiles that include differently controlledtiming of communication of data of the different data sources from thehub to the base station. For at least some embodiments, a data profileof at least one data source of the hub controls timing of communicationof data of the at least one data source according to more than one typeof controlled timing based on characteristics of the data of the atleast one data source.

Real-time, periodic, and scheduled transmissions are unique transmissiontypes on the link layer. However, different data movement manifestationscan occur in the context of the application layer. For an embodiment, anapplication layer transmission mode includes a store and forward mode.For an embodiment, the store and forward mode includes locally storingin memory one or many device datums to aggregate prior to sending thedata over the network using one of the link layer mechanisms. Thecombination of data processing and/or routing and the selection of alink layer transmission mechanism creates an application layertransmission mechanism. For example, data from a sensor of a data devicecan be collected in a local buffer of the data device until the bufferreaches X capacity and then the data device (as dictated by the dataprofile of the data device) transmits that data immediately. This is anexample of an application layer “store and forward” mechanism that isbuilt with a real time link layer transmission combined with datastorage and processing functions from the data profiles.

For an embodiment, an application layer transmission mode as defined bythe data profile of a data device includes a data pull mode. For anembodiment, the data pull mode cumulatively storing live datum untilrequested by a user. For example, through the data profile, a datadevice may be directed to store the latest temperature reading andtransmit that reading over the network when requested by a user via aweb console through a top down route via the base station and networkmanagement element.

At least some embodiments further include updating, by the networkmanagement element, the profile of one or more of the data sources. Atleast some embodiments further include adaptively updating the profileby a network operation center based on data communication activity of atleast the base station. For at least some embodiments, the datacommunication activity includes network traffic congestion. For at leastsome embodiments, the data communication activity includes wirelesscommunication between the hubs and the base station, and communicationbetween the data sources and the hubs. For at least some embodiments,the data communication activity includes a composition of data trafficbetween real-time traffic, scheduled traffic, and periodic traffic. Forat least some embodiments, the data profile is updated based on at leastone of a data load of the network, a user selection, customeracquisition, or application.

For at least some embodiments, the hub autonomously updates a dataprofile of a data device based on a sensed orientation of the hub of thedata device. For an embodiment, the hub pushes the data profile updateto the network management element. For example, when the orientation ofthe hub is placed upside down, this sensed orientation of the hub can besensed, and the data profile of a data device connected to the hub canbe adaptively updated to operate in a store and forward mode. For anembodiment, orientation of the hub is sensed and the data profile isupdated based on the sensed orientation to affect radio transmissionparameters of the wireless communication between the hub and the basestation. For example, the orientation of the hub can be detected using a9-axis IMU (accelerometer, gyroscope, magnetic sensor, all sensing 3orientations). Based on the sensed orientation of the hub, the dataprofile of the data device connected to the hub is adaptively updated todictate, for example, the MCS, repetition, and/or other radio parametersto adjust for loss of gain from antenna or other link budget factorsthat are affected by the orientation of the hub.

For at least some embodiments, the data profile sets a packet size ofcommunication of data of a data source that is communicated through thewireless link. For an embodiment, the packet size is selected to helpreduce overhead—and save the shared resource (wireless link). Further,for an embodiment, the selected data profile includes a selected MCS(modulation and coding scheme) based on the data source and theapplication being served.

For an embodiment, the packet size and/or list of datums that aretransmitted over the network is updated based upon an “active/notactive” flag. For an embodiment, setting the flag may come fromdirecting sensing on the hub (for example, an IMU, GPS, temperature) ormay come into the data profile directly from the sensor as a flag. Bothsides of the wireless link (hub and base station) need to a priori knowthe packet size in order to support the wireless communication betweenthe hub and the base station.

For at least some embodiments, the data profiles include preamble codes,and wherein for real-time communication, the preamble codes are insertedinto packets of the data sources to uniquely identify the data source ofthe packet during real-time communication. At least some embodimentsfurther include the network management element selecting the preamblecode for the data source based on a historical analysis of real-timetransmission timings of the hub of the data source and other datasources. For an embodiment, different preamble codes are allocated todata sources that historically report within a margin of time, andsimilar codes are allocated to data sources that historically report atdisparate times. For an embodiment, different preamble codes areassigned to data devices base on a QoS (quality of service) to minimizecongestion of data traffic been the base station and the hubs.

At least some embodiments further include processing, by one of more ofthe hubs, the data of the data source, and communicating the processeddata through the wireless link to the base station. For an embodiment,the processing includes filtering the data. An embodiment includes onlycommunicating (reporting) a type of data if a threshold condition issatisfied. For an embodiment, the processing. For an embodiment, theprocessing includes synthesizing data of more than one data source. Foran embodiment, synthesizing includes combining the data of more than onedata source before reporting. For an embodiment, synthesizing includesfiltering data of one source based on values of data of a second datasource.

FIG. 12 shows a plurality of hubs 1210, 1290 that communicate data ofdata sources 1211, 1212, 1213, 1214, 1215 through a shared resource to abase station, according to an embodiment. As shown, the data sources1211, 1212, 1213, 1214, 1215 are connected to the hubs 1210, 1290. Thehubs 1210, 1290 communicate through modems 1230, 1232 to a modem 1245 ofthe base station 1240 through the wireless links. For an embodiment, thewireless links are a shared resource 1299 that has a limited capacity.The described embodiments include data profiles which are utilized toprovide efficient use of the shared resource 1299. The base station mayalso communicate with outside networks 1270, 1280.

As previously described, it is to be understood that the data sources1211, 1212, 1213, 1214, 1215 can vary in type, and can each require verydifferent data reporting characteristics. The shared resource 1299 is alimited resource, and the use of this limited resource should bejudicious and efficient. In order to efficiently utilize the sharedresource 1299, each of the data sources 1211, 1212, 1213, 1214, 1215 areprovided with data profiles 1221, 1222, 1223, 1224, 1225 that coordinatethe timing (and/or frequency) of reporting (communication by the hubs1210, 1290 to the base station 1240 through the shared resource 1299) ofthe data provided by the data sources 1211, 1212, 1213, 1214, 1215.

For an embodiment, a network management element 1250 maintains adatabase 960 in which the data profiles 1221, 1222, 1223, 1224, 1225 canbe stored and maintained. Further, the network management element 1250manages the data profiles 1221, 1222, 1223, 1224, 1225, wherein themanagement includes ensuring that synchronization is maintained duringthe data reporting by the hubs 1210, 1290 of the data of each of thedata sources 1211, 1212, 1213, 1214, 1215. That is, the data reported byeach hub 1210, 1290 of the data of the data sources 1211, 1212, 1213,1214, 1215 maintains synchronization of the data reporting of each ofthe data sources 1211, 1212, 1213, 1214, 1215 relative to each other.Again, the network management element 1250 ensures this synchronizationthrough management of the data profiles 1221, 1222, 1223, 1224, 1225.The synchronization between the data sources 1211, 1212, 1213, 1214,1215 distributes the timing of the reporting of the data of each of thedata sources 1211, 1212, 1213, 1214, 1215 to prevent the reporting ofone device from interfering with the reporting of another device, andprovides for efficiency in the data reporting.

For at least some embodiments, the network management element 1250resides in a central network location perhaps collocated with multiplebase stations and/or co-located with a network operations center (asshown, for example, in FIG. 6). For an embodiment, the networkmanagement element 1250 directly communicates with the base station 1240and initiates the transfer of data profiles across the network via thebase station 1240 to the hubs 1210, 1290.

For at least some embodiments, data profiles are distributed when newhubs are brought onto the network, when hubs change ownership, or whenthe hubs are re-provisioned. Other changes to data profile contentsoutside of these situations are more likely addressed by sync packets(for an embodiment, a sync packet is a packet to update the value of aspecific field inside of a data profile, but not necessarily updatingthe structure of the data profile) were only small changes to profilefields are required.

As described, the data profiles 1221, 1222, 1223, 1224, 1225 controltiming of when the hubs 1210, 1290 communicate the data of the datasources 1211, 1212, 1213, 1214, 1215 through the shared resource 1299.Accordingly, the described embodiments coordinate access to the sharedresource 1299 to insure optimal usage of the network resource to avoidcollisions between packets, the transmission of redundant information,and to reshape undesired traffic profiles.

NBIOT

At least some of the described embodiments can be utilized forimplementations of NBIOT (Narrow Band Internet of Things). FIG. 13 showsa series of NBIOT communications between a server 1310, a base station1320, a NBIOT (narrow-band internet of things) modem 1330 of a hub, andthe hub 1340, according to an embodiment.

As previously described, for an embodiment, the server 1310 schedulescommunication between the base station and a plurality of hubs. For anembodiment, this includes the server providing the base station 1320with a schedule and metadata 1350. That is, the base station 1320receives the scheduled communication.

As previously described, for an embodiment, each hub 1340 is provided adata profile that includes a periodicity, an offset, and a carrierfrequency based on the scheduled communication. For an embodiment, thisincludes the base station 1320 providing the schedule of the server 1310to the hub 1340 as depicted by 1352 through a wireless link.

As previously described the base station 1320 receives uplink wirelesscommunication from each of the plurality of hubs according to the dataprofile of each of the hubs and according to the scheduledcommunication. For an embodiment, this includes the hub 1340 providingthe NBIOT modem 1330 with a data packet grant and meta-data 1352, andthe NBIOT modem 1330 communicating an RRC (radio resource control)EarlyDataRequest-NB 1354 to the base station 1320 through the wirelesslink.

As previously described, at least some embodiments include the basestation 1320 simultaneously broadcasting acknowledgements of receptionof the uplink wireless communication from each of the plurality of hubs.At least one of the plurality of hubs receives and determines whetheruplink wireless communication from the at least one of the plurality ofhubs was successfully received based at least the periodicity, theoffset, and the carrier frequency of the data profile of the at leastone of the plurality of hubs. For an embodiment, this includes theserver 1310 and/or base station 1320 communicating a broadcastacknowledgement 1356 that can include RRCEarlyDataComplete-NB to the hub1340.

Specifically as related to NB-IOT, for an embodiment, theRRCEarlyDataRequest message is used by a hub (for example, userequipment (UE)) for uplink transmission. That is, the scheduled uplinktransmission uses an RRCEarlyDataRequest message as specified in NB-IOT.

Further, specifically as related to NB-IOT, for an embodiment, accordingto an NB-IOT data-flow, the RRCEarlyDataComplete message is used tocomplete the data transmission operations at UE. For an exemplary datatransmission mode, the simultaneously broadcasting acknowledgements areused to complete the data transmission operations at hub (or UE), andthe simultaneously broadcasting acknowledgements include theRRCEarlyDataComplete message.

As previously stated, for an embodiment, the data profile includes aperiodicity, an offset, and a carrier frequency based on the scheduledcommunication. For an embodiment, the periodicity includes a Datatransmission Period in terms of H-SFN, SFN and SF. For an embodiment,the offset includes a Start Hyper system frame number (H-SFN), systemframe number (SFN) and subframe number for data transmission.

For an embodiment, the data profile further includes a packet size,which for an embodiment includes a maximum TBS (transport block size)for an uplink data packet.

Further, at least some embodiments include a retransmission mechanism incase of failure. That is, the simultaneously broadcastingacknowledgements indicate failure of an uplink wireless communication.The retransmission occurs upon determining failure of the uplinkwireless communication.

Although specific embodiments have been described and illustrated, theembodiments are not to be limited to the specific forms or arrangementsof parts so described and illustrated. The described embodiments are toonly be limited by the claims.

What is claimed:
 1. A method of communicating through a wireless link,comprising: scheduling, by a server, communication between a basestation and a plurality of hubs; receiving, by the base station, thescheduled communication; providing, to each hub, a data profile thatincludes a periodicity, an offset, and a carrier frequency based on thescheduled communication; receiving, by the base station, uplink wirelesscommunication from each of the plurality of hubs according to the dataprofile of each of the hubs and according to the scheduledcommunication, wherein the uplink wireless communication is includedwithin an uplink frame, wherein an uplink wireless communicationallocation of each of the plurality of hubs is within a different timeslot of the uplink frame than other of the plurality of hubs; andsimultaneously broadcasting, by the base station, acknowledgements ofreception of the uplink wireless communication from each of theplurality of hubs within a downlink frame; wherein a hub of theplurality of hubs receives the downlink frame that includes thesimultaneous broadcast acknowledgements and determines whether uplinkwireless communication from the hub was successfully received based on adetermination of which of one or more bits within the simultaneousbroadcast acknowledgements of the downlink frame includes acknowledgmentinformation of the hub based on scheduled time and frequency slots ofthe scheduled communication for the uplink wireless communication of thehub.
 2. The method of claim 1, wherein the uplink wireless communicationis transmitted by the plurality of hubs and received by the base stationthrough a satellite wireless link, and the base station simultaneouslybroadcasts the acknowledgements through the satellite wireless link. 3.The method of claim 1, further comprising: wherein reception of thesimultaneously broadcast acknowledgements by each hub is facilitated bythe data profile of the hub.
 4. The method of claim 3, wherein the dataprofile includes at least one time and frequency slot for uplinkcommunication of the hub.
 5. The method of claim 4, wherein the dataprofile further includes at least one time and frequency slot forreception of broadcast acknowledgments by the hub.
 6. The method ofclaim 1, wherein the scheduled communication that is provided to thebase station includes time slots and carrier frequencies, and includesan allocation of at least some of the time slots and subcarrierfrequencies.
 7. The method of claim 6, further comprising, allocating,by the base station, additional time slots and carrier frequencies. 8.The method of claim 7, wherein the allocating includes receiving, by thebase station, subsequent requests and demands that the base stationadapts and infills the additional time slots and carrier frequencies. 9.The method of claim 1, wherein the data profile of the user devicefacilitates reception of the simultaneously broadcast acknowledgementsthrough at least an acknowledgement period and an acknowledgement offsetincluded within the data profile of the hub that allows the hub todetermine when to receive simultaneously broadcast acknowledgements ofuplink wireless communication of the hub.
 10. The method of claim 1,wherein each simultaneously broadcast acknowledgement includesacknowledgement information of a plurality of hubs that transmitteduplink wireless communication within a corresponding period of timet2-t1, and subcarrier frequencies.
 11. The method of claim 1, whereinthe simultaneously broadcast acknowledgements include simultaneouslymulticast acknowledgements, wherein an acknowledgment for each of theuser devices within the simultaneously multicast acknowledgementsinclude a code that a corresponding set of hubs can decode.
 12. Themethod of claim 1, wherein an acknowledgment for each of the hubs withinthe simultaneously broadcast acknowledgements provides an acknowledgmentto the hub for uplink wireless communication within a specified numberof time slots and carrier frequencies.
 13. The method of claim 1,wherein the hub profile includes the periodicity, offset, and carrierfrequency for the uplink wireless communication, and an acknowledgementperiodicity, and an acknowledgement offset of acknowledgements of theuplink wireless communication within the simultaneously broadcastacknowledgements.
 14. A wireless system, comprising: a server, theserver operative to schedule communication between a base station and aplurality of hubs through a wireless link; the base station operativeto: receive the scheduled communication; provide to each hub a dataprofile that includes a periodicity, an offset, and a carrier frequencybased on the scheduled communication; receive uplink wirelesscommunication from each of the plurality of hubs according to the dataprofile of each of the hubs and according to the scheduledcommunication, wherein the uplink wireless communication is includedwithin an uplink frame, wherein an uplink wireless communicationallocation of each of the plurality of hubs is within a different timeslot of the uplink frame than other of the plurality of hubs; andsimultaneously broadcast acknowledgements of reception of the uplinkwireless communication from each of the plurality of hubs; wherein a hubof the plurality of hubs receives the downlink frame that includes thesimultaneous broadcast acknowledgements and determines whether uplinkwireless communication from the hub was successfully received based on adetermination of which of one or more bits within the simultaneousbroadcast acknowledgements of the downlink frame includes acknowledgmentinformation of the hub based on scheduled time and frequency slots ofthe scheduled communication for the uplink wireless communication of thehub.
 15. The wireless system of claim 14, wherein reception of thesimultaneously broadcast acknowledgements by each hub is facilitated bythe data profile of the hub.
 16. The wireless system of claim 15,wherein the data profile includes at least one time and frequency slotfor uplink communication of the hub.
 17. The wireless system of claim16, wherein the data profile further includes at least one time andfrequency slot for reception of broadcast acknowledgments by the hub.18. The wireless system of claim 14, wherein the hub profile includesthe periodicity, offset, and carrier frequency for the uplink wirelesscommunication, and an acknowledgement periodicity, and anacknowledgement offset of acknowledgements of the uplink wirelesscommunication within the simultaneously broadcast acknowledgements. 19.The method of claim 1, further comprising: monitoring reporting times ofdifferent data sources of different hubs over time; allocating preamblecodes to each of the data sources, wherein different preamble codes areallocated to different data sources that report within a margin of timeof each other; and inserting the allocated preamble codes into packetsof each of the data sources.